Skip to content

Add resources vendors directory - #2459

Open
BrendanBondurant wants to merge 6 commits into
graphql:sourcefrom
BrendanBondurant:add-resources-vendors-directory
Open

Add resources vendors directory#2459
BrendanBondurant wants to merge 6 commits into
graphql:sourcefrom
BrendanBondurant:add-resources-vendors-directory

Conversation

@BrendanBondurant

Copy link
Copy Markdown
Contributor

Closes #2458

Description

This PR adds a new resources/vendors page to the Resource Hub and places it in the Resources submenu below Tools & Libraries.

The new page creates a dedicated place for GraphQL vendors, instead of mixing vendor/company entries into other resource pages. Each vendor entry includes:

  • Logo
  • Vendor name
  • Short description
  • Website link
  • Optional GitHub link

I also added the initial vendor dataset in resources/vendors/data.ts.

Implementation notes

  • Vendor entries are modeled at the company/vendor level, not the product level.
  • This is intentionally separate from the existing Tools & Libraries catalog, which is more product/library oriented.
  • Descriptions are currently free-form, but kept short for consistency on the listing page.
  • Vendor entries are sorted alphabetically.

Open questions

This PR implements the page, but there are still a few content/modeling decisions we may want to confirm:

  • Should this page include only GraphQL-focused vendors, or also broader vendors with significant GraphQL support?
  • Do we want a hard character limit for descriptions?
  • Should new vendor entries require editorial/reviewer approval before being added?
  • Should vendor data continue to use a dedicated structure, or should it be unified with existing resource entry types later?

Testing

  • Verified the new page renders at /resources/vendors
  • Verified the submenu link appears in the Resources navigation
  • Verified vendor cards render logo, name, description, and links correctly
  • Verified alphabetical sorting
  • Verified optional GitHub links only show when present

Screenshots

Screenshot 2026-06-30 at 09 59 27

--

Screenshot 2026-06-30 at 09 59 56

@vercel

vercel Bot commented Jun 30, 2026

Copy link
Copy Markdown

@BrendanBondurant is attempting to deploy a commit to the The GraphQL Foundation Team on Vercel.

A member of the Team first needs to authorize it.

Comment thread src/resources/vendors/data.ts Outdated
"WunderGraph builds Cosmo, an open-source platform for GraphQL Federation at scale with a schema registry, composition, routing, and analytics.",
url: "https://wundergraph.com/",
github: "wundergraph",
},

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Probably worth a few extra ones?

  • Azure API Managerment,
  • WSo2 API Manager
  • IBM's StepZen
  • Apigee
  • Kong Gateway

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure, I will add those in now

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@martinbonnin are these really GraphQL vendors? do they have any GraphQL features?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would say they're not GraphQL first but they are GraphQL compatible and it's a nice thing to know overall for users out there to be aware of those options.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

its not an important enough point for me to hold the PR, but I can't see what these options mean for GraphQL users?
when they click on them, what will they find out?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what these options mean for GraphQL users?

Means there's a wide ecosystem of tools compatible with GraphQL that they can explore. More options is good for GraphQL users.

its not an important enough point for me to hold the PR

Same for me. Opinion not strongly held. I'll let @BrendanBondurant decide what he likes best.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@martinbonnin and @Urigo, apologies for the delayed response. I was AFK for a few days.

Since they are compatible and do have GraphQL features, I am inclined to leave them in. We could make the descriptions more explicit so a GraphQL user knows what they are getting.

Comment thread src/resources/vendors/data.ts Outdated
@BrendanBondurant
BrendanBondurant marked this pull request as ready for review July 2, 2026 15:14
@saihaj
saihaj requested a review from martinbonnin July 8, 2026 22:30
@vercel

vercel Bot commented Jul 28, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
graphql-github-io Ready Ready Preview, Comment Jul 28, 2026 7:09pm

Request Review

@saihaj

saihaj commented Jul 28, 2026

Copy link
Copy Markdown
Member

I wonder if we can source all the data from here https://landscape.graphql.org since that is actively maintained

source: https://github.com/graphql/graphql-landscape

@saihaj saihaj left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

on resource page this page is not really discoverable

Image

Comment thread src/resources/vendors/data.ts Outdated
@martinbonnin

Copy link
Copy Markdown
Contributor

I wonder if we can source all the data from here https://landscape.graphql.org/ since that is actively maintained

@saihaj I agree in principle but in practice, the graphql-landscape repo is out of the TSC control (at least I can't merge there) and maintaining it comes with some friction. I'll inquire about it but in the meantime, I'm fine keeping a less official but more active list here.

@saihaj

saihaj commented Aug 19, 2026

Copy link
Copy Markdown
Member

I wonder if we can source all the data from here https://landscape.graphql.org/ since that is actively maintained

@saihaj I agree in principle but in practice, the graphql-landscape repo is out of the TSC control (at least I can't merge there) and maintaining it comes with some friction. I'll inquire about it but in the meantime, I'm fine keeping a less official but more active list here.

I wasn't aware of that. we should for sure then keep it here then and maintain ourselves. I just don't want to miss any that exist there to start with and bring them here.

Co-authored-by: Uri Goldshtein <uri.goldshtein@gmail.com>
@martinbonnin

Copy link
Copy Markdown
Contributor

@Urigo can you approve this PR (if you're okay with it of course!)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add a vendors overview page under Resources

4 participants